Method and apparatus for providing a toll service and flexible toll device

ABSTRACT

A system, mobile device, backend server, and RFID toll module work in cooperation to automatically pay vehicular tolls to a toll agency that operates toll stations along a roadways travelled by the user of the mobile device. Upon approaching a toll station the mobile device enables the RFID toll module. The toll reader at the toll station transmits a toll reader signal that is received by the RFID toll module, which responds by transmitting a unique identifier. The unique identifier is associated with the mobile device at a toll account maintained by a toll service backend server. Upon completion of a toll transaction, the RFID toll module indicates the transaction to the mobile device, which forwards toll transaction information to the toll service backend server for payment from the toll account to the toll agency.

CROSS REFERENCE

This application is a divisional application of U.S. patent applicationSer. No. 14/091,678, filed Nov. 27, 2013, which was a utility conversionof provisional application No. 61/730,495, filed Nov. 27, 2012, thecontents and disclosure of each of which are hereby incorporated byreference in their entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to automated vehicular tollcollection, and more particularly to mobile smartphone applications thatwork in conjunction with an RFID-enabled module for transacting andprocessing tolls.

BACKGROUND

Tollways and tollbooths, such as are commonly used on turnpike highwaysand other toll roads, are used to collect tolls to pay for roadmaintenance and other costs associated with the toll road. While in thepast, and to some extent it is still the case, drivers were forced tostop and pay with currency at each toll plaza, it is increasingly commonto use electronic toll collection that allows drivers to simply drivethrough a toll plaza at ordinary speed. In some automated toll systems,a radio transponder, that can be active or passive, and is located inthe vehicle, is read by a radio signal as the vehicle passes under agantry in a toll plaza. The toll plazas are often operated by a tollagency, which may be a private agency or a government agency. Someexamples of toll agencies include SunPass and EZ-Pass. The transponder,typically being mounted in a vehicle, allows for little flexibility whenone changes vehicles or is using a rental car. A transponder also lacksthe ability to be secured so as to prevent toll fraud or allow tolls incase the vehicle (or transponder) is stolen.

The United States Department of Transportation (USDOT) released anIntelligent Transportation Systems (ITS) Strategic Research Plan for2010-2014 at the end of 2009. The ITS (its.dot.gov) website disclosesthe plan as assuming government investment of upwards of $100 millionper year for five years. The tolling industry handles its customer basein a somewhat parochial way. In actuality, anyone using public roadwaysmay be seen as a customer. Each tolling facility tracks customers fordata such as account information, volume and frequency of trips andwhere these customers reside. However, the existing agencies do littleto incentivize customers to increase user usage of toll agency services.Marketing and rewards programs are rarely used. Therefore, toll agenciesfocus on reducing costs while increasing reliability of technologysolutions (such as ISO 18000 6C reader tag protocol forinteroperability), greater efficiencies in logging individuals highwayuse, and better quality imaging technologies (such as high-definition),to collect delinquent fees from toll evaders, are seeking improvedsystems.

Current toll options include RFID Tags and Readers, and Transpondersused by Toll Companies like EZPass and SunPass, from providers such asKapsch lack interoperability. The US government issued a mandate forinteroperability among various state tolling systems by 2016,accompanied by a plan to distribute and share revenues between theplethora of companies and agencies. A less-desirable default option hasbeen the Toll-by-Plate system, where, rather than having a transponder,the gantry at a toll plaza captures an image of the vehicle's licenseplate and charges the toll to the owner or registered user associatedwith the license plate number. However, this system is not sufficientlyaccurate nor convenient; visibility may often be obscured withobstacles, highway gridlock, and weather, and costs are typically higherthan with a more targeted system. Customers unaware of the Toll-by-Plateoperation who have not established an account with the agency willtypically be charged somewhat punitive charges in addition to the toll.

Accordingly, there is a need for a method and apparatus for an automatedtolling system that provide the toll account owner more flexibility andsecurity in tolling, and which preserves the accuracy and reliability ofconventional automated tolling systems.

SUMMARY

The embodiments described herein describe a mobile device incommunication with a RFID toll module that is capable of communicatingwith a wide variety of tolling systems and provide instantcross-platform, cross-protocol interoperability. The hardware andsoftware based application integrates RFID, mobile smartphone andbusiness-server based technologies. Embodiments can be customizable towork with current tolling technologies that are applied by toll agenciesand providers. Embodiments provide a user-friendly paradigm for users tomanage and pay their toll-bills. Embodiments disclosed herein are bothportable and self-contained, and easily accessible, user-friendly, lightand portable for users of the highway network in possession of mobiledevices.

Embodiments include a radio frequency identification (RFID) toll tag anda toll application for payment of tolls that can be either embedded intothe circuitry of a mobile device, or connectable to the mobile devicethrough one of several interfaces, including but not limited to audiojack, micro-USB, BlueTooth or proprietary connector interface, such asfor an iPhone. The RFID toll module can be embodied as a dongle or aprotective cover/sleeve.

In some embodiments, a toll reader transmits a radio-frequency signalthat is received by the RFID toll module, which has an RFID tag. TheRFID tag, which can be in the form of an active or semi-passive RFIDchip, becomes energized by the reader signal, which can comply with thestandards of the EPC™ Class-1 Generation-2 RFID Protocol forCommunication within the range of 860-960 MHz. A passive system cantransmit out “back-scatter”, which acts as Morse code that is sent backto the reader. A more active RFID chip mirrors the reader's frequency totransmit back the requisite data to it. The tag or chip then passesinformation to the high-level application either integrated into theRFID tag or chip, which is returned to the toll application on themobile device. The RFID tag or chip can provide an identifier which isunique to the RFID tag, and the mobile device can then collect thevehicle/user's current location. There can be a memory in the RFID tollmodule to store or buffer the data transfers. The toll application, viathe mobile device, transfers transaction information to a backend serverof the toll service for processing. At the toll service backend, whenthe mobile device's location match those of the toll reader at the tollstation, within an approved margin of error, the payment for the tollcan be verified and processed. This is a further step of reconciliationand verification which enhances security.

The toll application is portable across various existing national andglobal systems, and compliant with multiple standards. The user sets uptheir account and may implement, for example, a parent-childrelationship, with multiple sub-accounts for different user-memberswithin a family/organization. When the RFID toll module is connected tothe mobile device, it must be activated and registered to the tollapplication on the mobile device with the toll service. Thereafter, theRFID toll module will not work with another subscriber identity module(SIM) card. In order to use the RFID toll module with another SIM card,it must be deregistered and deactivated from the first one. Therelationship always remains one-to-one. On the other hand, a single tollaccount can be associated with multiple RFID toll modules/mobile devicesfor multiple sub-accounts of the toll account.

A key factor in the system is portability and interoperability acrossplatforms and RFID protocols, allowing the toll application and the RFIDtoll module to be used in various geographical areas and across multipletoll-companies. A possible mode of interface for communication betweenthe component and the phone, but not limiting, could be a SerialPeripheral Interface bus (SPI) interface that implements a synchronousserial data link standard, operating in a full duplex mode. Thecommunication between devices occurs in master/slave mode where themaster device initiates and controls data communication, which in thisscenario could be the phone itself.

In some embodiments, as the user's mobile device is traveling atvehicular speeds (above pedestrian speeds) and approaches toll stationlocation (mapped into the application), the toll application selects theproper RFID tag for the approaching system, which includes the properprotocol fields for the different agencies using the same technology,and turns-on the RFID tag to receive the reader signal.

BRIEF DESCRIPTION OF THE FIGURES

The accompanying figures, where like reference numerals refer toidentical or functionally similar elements throughout the separateviews, together with the detailed description below, are incorporated inand form part of the specification, and serve to further illustrateembodiments of concepts that include the claimed invention, and explainvarious principles and advantages of those embodiments.

FIG. 1 is a block diagram of toll system architecture, in accordancewith some embodiments;

FIG. 2 is an isometric view of a mobile device and sleeve tagged with anRFID toll module connected to the phone, in accordance with someembodiments;

FIG. 3 is an isometric view of a mobile device and sleeve tagged with anRFID toll module that is placed over, and connected to the mobiledevice, in accordance with some embodiments;

FIG. 4 is system diagram of a toll system including a toll plaza, tollagency back end, and toll service back end, in accordance with someembodiments;

FIG. 5 is system diagram for a toll system, in accordance with someembodiments;

FIG. 6 is flow chart diagram of a method for automated tolling, inaccordance with some embodiments;

FIG. 7 is a flow chart diagram of a method for completing a transactionin an automated tolling system, in accordance with some embodiments;

FIG. 8 is a block diagram of a financial system for conducting automatedtolling through a toll service, in accordance with some embodiments;

FIG. 9 is a system diagram of an automated tolling system forreconciling toll transactions, in accordance with some embodiments; and

FIG. 10 is a system diagram of a mobile device and associatedtransponder for automated tolling, in accordance with some embodiments.

Skilled artisans will appreciate that elements in the figures areillustrated for simplicity and clarity and have not necessarily beendrawn to scale. For example, the dimensions of some of the elements inthe figures may be exaggerated relative to other elements to help toimprove understanding of embodiments of the present invention.

The apparatus and method components have been represented whereappropriate by conventional symbols in the drawings, showing only thosespecific details that are pertinent to understanding the embodiments ofthe present invention so as not to obscure the disclosure with detailsthat will be readily apparent to those of ordinary skill in the arthaving the benefit of the description herein.

DETAILED DESCRIPTION

Embodiments include a system for automated payment of tolls thatincludes a toll reader at a toll station, and a RFID toll module that iscoupled to a mobile device. The mobile device executes a tollapplication, and the RFID toll module includes at least one RFID tagthat is configured to communicate with the toll reader using a RFIDprotocol for a toll transaction. A RFID tag selected to conduct the tolltransaction communicates an identifier to the toll reader in response tobeing read by the toll reader during the toll transaction. The RFID tollmodule communicates transaction information to the toll application onthe mobile device upon completion of the toll transaction. The systemfurther include a toll service backend server that maintains a tollaccount that is associated with the mobile device, and to which the tollapplication on the mobile device communicates the transactioninformation. The toll service backend reconciles payment of the tollwith a toll agency that operates the toll reader, using funds from thetoll account.

Embodiments further include a method for automated toll transactionsthat includes determining, by a mobile device, that the mobile device isapproaching a toll station, and in response the mobile device enabling aRFID toll module that is coupled to the mobile device. Upon beingenabled, the RFID toll module receives a toll reader signal at the tollstation and responds to the toll reader signal in a toll transaction.The method further includes the mobile device receiving from the RFIDtoll module an indication of the toll transaction, and in response themobile device reporting the toll transaction to a toll service backendserver via a cellular infrastructure for payment of the toll from a tollaccount associated with the mobile device and maintained by the tollservice backend server.

In some embodiments, the user's mobile device has the toll applicationfor paying and managing tolls while travelling in any vehicle and acrossmultiple Regions and Toll Companies. This solution therefore allows auser to pay tolls in, for example, a rental car. The user's instance ofthe toll application is installed on the mobile device, and isregistered to the user's toll account on the toll service backendsystem, and can execute on the mobile device as a background process atmost times for conservation of power and device resources. At the sametime, either as a physically and electronically attached component, oras a built-in and embedded module, an RFID toll module, including one ormore RFID tags or chips with encoded logic for communicating to a tollreader. The RFID toll module can also include a processor (e.g.microprocessor or microcontroller) and other encoded logic. The tollapplication can be run in the background and can periodically send theuser's location to the toll service backend server. While operating inthe background, the toll application is in a sleep state, and remainsthere until activated by a command from, for example, the toll servicebackend server, which is typically generated by logic comparing thelocation of the mobile device with the locations of known toll stations.Once a transaction occurs and the RFID tag is read at a toll station,the toll application can, in some embodiments, transmit useridentification and location information along with directionalinformation and a timestamp to the toll service backend server, whilethe toll reader at the toll station sends analogous information to atoll agency backend server.

FIG. 1 is a block diagram of toll system architecture 100, in accordancewith some embodiments. Radio frequency identification (RFID) module 102operates as a wireless toll transponder that can be read by a tollreader 150, and it communicates with a mobile device 104 over aconnection 106. The mobile device is a cellular telephone device thatincludes other functionality, and is of the type of cellular phonecommonly referred to as a “smartphone.” The RFID toll module include oneor more selectable RFID tags 108, where each RFID tag 108 can beconfigured for a different RFID protocol that can be used by differenttoll readers 150 for different toll agencies. Each RFID tag 108 includescircuitry for receiving a toll reader signal 152, and responding to thetoll reader signal 152 by transmitting an identifier that is unique toeach RFID tag 108. The RFID tags 108 use a protocol such as, forexample, that specified by ISO/IEC 18000-6C, ISO/IEC 18000-6B, theInteragency Group (IAG) Time Division Multiplexing (TDM) standard, orother known RFID interface standards. A conventional RFID tolltransponder only contains a RFID tag 108, however, the RFID toll module102 further contains a processor 112 that is coupled to a memory 110that contains instruction code that is executed by the processor 112 tooperate the RFID toll module 102. For one, the processor 112 can controlswitching of the various RFID tags 108 so that the correct RFID tag 108is configured to receive and respond to the toll reader signal 152, aswell as to be able to communicate with the processor 112. Logiccircuitry 114, that is also controlled by the processor 112, can performtasks such as switching, energy harvesting from the toll reader signal152, and other functions. The processor 112 is further coupled to aninterface 116 that allows the RFID tag device 102 to communicate withthe mobile device 104 over connection 106. The RFID toll module 102 canbe passive, active, or semi-active. An active RFID toll module deviceincludes a battery (not shown) to power the various components. Apassive RFID toll module device 102 scavenges energy from the readersignal 102, as is known, to store energy that is then used to respond.The connection 106 can be a wired or wireless connection, such as auniversal serial bus (USB) connection, audio connection, audio jackconnection, or other connections, as will occur to those skilled in theart.

The mobile device 104 has a similar interface 118 that is coupled to aprocessor 120 of the mobile device 104. A memory 122 is coupled to theprocessor 120 and contain instruction code for operating the mobiledevice 104, and includes a toll application 124. The toll application isable to access resources of the mobile device, such as a cellulartransceiver 126 and a satellite positioning system receiver such aGlobal Positioning System receiver (GPS) 130. The mobile device alsocontains additional circuitry and logic for carrying out various tasksand operations of the mobile device. The cellular transceiver 126communicates with a cellular infrastructure 134 using cellular signals132.

The RFID toll module 102 and the mobile device 104 are co-located, andtaken by a user in a vehicle. The toll application 124 can periodicallyreport location information to a toll service back end server 138 thatis operated by a toll service provider to which the user has subscribed.The location information is transmitted to the toll service backendserver over the cellular infrastructure 134 that can forward theinformation through a network 136 such as the Internet. When the vehicleis approaching a toll station (e.g. a toll plaza, or toll booth) that isRFID enabled, the toll application can communicate with the RFID tollmodule 102 to configure it for the appropriate RFID tag 108. The tollservice backend server 138 can maintain a map of toll stations anddetermine from the received location information that the vehicle isapproaching a toll station. Alternatively, the toll application 124 candetermine the approach of a toll station locally, in the mobile device,using, for example, a mapping application and location information fromthe GPS receiver 130. The toll application 124, via the interface 118 ofthe mobile device 104, communicates configuration instructions to theprocessor 112 of the RFID toll module 102, indicating the selectedconfiguration to be used. In response, the processor 112 can configurethe RFID toll module 102 so that the selected RFID tag 108 is connectedto receive and respond to toll reader signals 152. In some embodimentsone or more protocol stacks for various toll reader protocols can bestored in the RFID toll module 102 which can be loaded into the RFID tag108. In some embodiments the protocol stack can be provided by themobile device 104 upon enabling the RFID toll module 102.

As the vehicle approaches a toll station it is detected by the tollreader 150 such as by use of magnetic sensors in the traffic lanecorresponding to the toll reader 150. The toll reader signal 152 isreceived by the RFID tag 108, which responds with the identifier of theRFID tag 108. The toll reader signal 152 can, in some embodiments,contain information, such as an identifier of the toll reader 150. Thetoll reader 150 and toll agency backend server 146 are operated by atoll agency that can be contracted with a governmental agency. Examplesof toll agencies include, for example, those known as SunPass, EZPass,and FasTrack. Upon receiving a response from the RFID tag 108, the tollreader 150 communicates the transaction information to a toll agencybackend server 146 over a network 148, such as the Internet. Likewise,the RFID toll module 102 communicates transaction information to thetoll application 124, which in turn transmits the transactioninformation to a toll service backend server 138. The toll servicebackend server 138 maintains an account 140 that corresponds to the RFIDtoll module 102 and/or the toll application 124. The toll agency backendserver 146 and the toll service backend server 138 include hardware tosupport at least one processor that executes instruction code cause theservers to perform the various tasks described herein, among other task.

FIG. 2 is an isometric view 200 of a mobile device 202 and sleeve 204tagged with an RFID toll module connected to the mobile device 202, inaccordance with some embodiments. The sleeve 204 can be a cover orjacket that fits over the phone 202. The sleeve contains circuitry 220for a RFID toll module, such as RFID toll module 102 of FIG. 1, andincludes a processor 222, RFID tag 224, and other logic 226 (e.g.memory, switches, and so on). The mobile device 202 includes variousports and interfaces, such as a speaker 206, USB connector 208, and anaudio jack input 210. The sleeve can connect to the phone using one ofthese, or some other modality. For example, the sleeve 204 can containan audio receiver 212 that corresponds to the speaker 206 for receivingaudio signals that are interpreted by the circuitry 220. In someembodiments the sleeve contains a USB connector 214 that corresponds to,and mates with the USB connector 208 of the mobile device 202, andcommunication can occur using a USB protocol. In some embodiments thesleeve 204 can contain an audio connector 218 that corresponds with theaudio jack connector 210 of the mobile device 202.

FIG. 3 is an isometric view 300 of a mobile device 202 and sleeve 204tagged with an RFID toll module circuit 220 that is placed over, andconnected to the mobile device 202, in accordance with some embodiments.The sleeve 204 can be fabricated of a flexible material, as indicated byarrows 302, allowing the sleeve 204 to be easily placed on phone 202such that it will be held in place on the phone 202. The sleeve can besubstantially the same as that shown in FIG. 2. While shown as aflexible sleeve or cover in FIGS. 2-3, it will be appreciated by thoseskilled in the art that the RFID toll module can be packaged in numerousother forms.

FIG. 4 is system diagram of a toll system 400 including a toll plaza408, toll agency back end 416, and toll service back end 418, inaccordance with some embodiments. A vehicle travels in a traffic lane406 towards the toll plaza 408. The vehicle carries a driver orpassenger who owns or possesses a mobile device 404 that coupled to aRFID toll module 405 such as RFID toll module 102 of FIG. 1. As thevehicle 402, and therefore the mobile device 404 and RFID toll module405 approach the toll plaza 408, the mobile device 404 can be incommunication with the toll service backend server 418 (which can be acluster of several different hardware entities and different servers),the mobile device 404 enables the RFID toll module 405. The mobiledevice, which is executing a toll application, can enable the RFID tollmodule 405 based on a command from the toll service backend server 418,which is in response to location information transmitted to it from themobile device 404, or the mobile device 404 can determine its proximityto the toll plaza 408 on its own using location information and amapping application. When the vehicle is within a certain distance fromthe toll plaza 408, a toll reader 410 can detect the vehicle and begintransmitting a reader signal 412. The RFID toll module 405 receives thereader signal 412 and responds 414 with an identifier. The identifier istransmitted to the toll agency backend server in a transaction record.Likewise, the mobile device 404 transmits transaction information to thetoll service backend server 418. The transaction can be reconciled 420between the toll agency backend server 416 and the toll service backendserver 418. The transaction information can include, for example,identity, geographical location, a timestamp, and the direction oftravel for processing by the toll service backend server 418. The tollreader 410 can transmit similar information to the toll agency backendserver 416.

FIG. 5 is system diagram for a toll system 500, in accordance with someembodiments, and shows a process flow of a system such as that shown,for example, in FIG. 4. A mobile device 502 having a toll application503 is coupled to a RFID toll module 504 over a connection 505. Themobile device 502 and RFID toll module 504 can be substantially similarto those shown in FIG. 1. A toll service backend 506 can include anapplication server 508, a transaction server 510, and a web server 514.Furthermore, the backend 506 maintains an account 512 associated withthe mobile device 502 and/or the RFID toll module 504. The tollapplication can communicate with the application server (e.g. via thecellular infrastructure and Internet) to process tolls on behalf of theuser of the mobile device 502. The application server 508 communicateswith the transaction server 510 to log and record toll transactions. Thetransaction server also communicates with the toll agency backend server520 for reconciliation of toll payments. The web server 514 provides aninterface for a user to access the user's account 512, add fund, viewtransactions, and so on. The RFID toll module 504 can be read by a tollreader 516 at a toll plaza or toll station. When being read, the tollreader 516 can transmit some information to the RFID toll module 504,such as an identifier of the toll reader, for verification. The tollapplication 503 can transmit transaction information, including, forexample, the identifier of the toll reader 516, a time stamp, locationinformation, and so on, to the application server 508. The applicationserver 508 can also provide the toll application 503 with accountinformation for the account 512 that can be displayed on a display ofthe mobile device 502.

FIG. 6 is flow chart diagram of a method 600 for automated tolling, inaccordance with some embodiments. Each box in the follow chart, and inflow charts of other subsequent figures, represent an abstraction of oneor more processes or operations undertaken various entities in thesystem. The method 600 can start in process 602 where the tollapplication is installed on the mobile device, and it is registered witha toll service backend and associated with an account maintained by thetoll service backend server. The account has a one to one correspondencewith an identifier of the mobile device, such as, for example, anidentifier on a subscriber identity module (SIM card) in the mobiledevice. If the mobile device is not registered, the toll service canrespond with a message asking the user to set up an account. The tollapplication is also able to communicate with a RFID toll module. Inprocess 604 the toll application determines it is approaching a tollstation or toll plaza. The toll application can make the determinationby, for example, providing the backend server with periodic locationupdates and in response the backend server can message the tollapplication when it is approaching a toll station. Alternatively, thetoll application can make the determination locally using locationinformation and a mapping application. In response, the toll applicationcommunicates with the RFID toll module to configure it to be read at thetoll station as the vehicle passes through the toll station. In process606 the RFID toll module is read by the toll reader, and receives orgenerates transaction information, which is communicated to the tollapplication. In process 608 the toll application transmits thetransaction information to the toll service backend, such as by acellular infrastructure. The toll service backend can determine whetherthere are sufficient funds available in the user's account to pay forthe toll in process 610. Assuming there are sufficient funds, in process614 the payment can be processed (immediately, or later in a batchoperation), and the account updated accordingly. If in process 610 thereare not sufficient funds available, the method 600 proceeds to process612 where the toll service backend indicates such to the tollapplication, and indicates that the transaction failed. In someembodiments, however, the user can set up automatic replenishment sothat whenever the funds in the user's account falls below a presetvalue, a preset amount is transferred from the user's bank or charged tothe user's credit card, for example.

FIG. 7 is a flow chart diagram of a method 700 for completing atransaction in an automated tolling system, in accordance with someembodiments. The method 700 can start in process 702, where the tollapplication is installed and executing on a mobile device, andcommunicatively coupled to a RFID toll module. In process 704 the tollservice backend server periodically polls the toll application forlocation information. In process 706 the toll service backend serverdetermines whether the mobile device, based on the location information,is approaching a toll station. Alternatively, as described elsewhereherein, the toll application on the mobile device can make thisdetermination using a mapping application. If not, the method loopsbetween processes 706 and 704. When the toll service backend serverdetermines that the mobile device is approaching a toll station, inprocess 708 the backend server message the toll application to wake upthe toll application (assuming it was in a sleep mode or state), whichin turn configures the RFID toll module accordingly. In process 710 thetransaction completes with the toll application transmitting transactioninformation to the toll service backend service for payment andreconciliation with the toll agency. The method 700 can then end 712, orreturn to process 704.

FIG. 8 is a block diagram of a financial system 800 for conductingautomated tolling through a toll service, in accordance with someembodiments. The user's mobile device 802 executes a toll application804 that allows the user to pay tolls using a RFID toll module (notshown). The mobile device 802, under control of the toll application804, can communicate with a toll service server 806, which, among othertasks, maintains an account for the user, from which tolls are paid forthe user by the toll service. The user can add funds to the account fromthe user's bank or credit card 808. The toll service can likewise use abank 810 or other financial institution 810 to hold user funds in escrowuntil they are used to pay tolls. The toll service 806 can communicatewith a toll agency 812 that charges tolls to be paid by the tollservice. The toll agency can work with one or more banks 814, 816 forreceipt of toll funds, which can be transferred to the banks 814, 816from the toll service bank 810.

FIG. 9 is a system diagram of an automated tolling system 900 forreconciling toll transactions, in accordance with some embodiments. Thesystem 900 show parallel processes for processing toll payment. There isa user side 902 and a server or reconciliation side 904. On the userside 902 a user 906, using, for example, the toll application on amobile phone or a computer with Web access, can add funds to the user'saccount by, for example, contacting the toll service 908 (e.g. a serverof the toll service). The process can involve the user's bank 910 andthe toll service 908 performing payment processing 912, and funds arethen added to the users toll account 914. The funds in the toll accountcan be used to pay tolls in accordance with the disclosure to one ormore different toll agencies. Upon success of the payment processing912, the user's account is updated to reflect addition of the funds.

On the reconciliation side 904, when it is time to reconcile payment oftoll (either upon the toll transaction occurring, or at a batchprocessing time), funds from the user's toll account 914 can be forwardfor payment processing 920 by the toll service 908 to a toll agency 922.Upon success of the payment processing 920, the funds are transferred tothe toll agency's bank 924. The successful transfer is then debited tothe user's account 914.

FIG. 10 is a system diagram 1000 of a mobile device 1002 and associatedtransponder RFID toll module 1005 for automated tolling, in accordancewith some embodiments. The mobile device 1002 includes a tollapplication 1004 in accordance with the disclosure. The mobile deviceand the RFID toll module 1005 operate in master-slave configuration asin, for example, that shown in FIGS. 1-3. However, the communication1008 between the mobile device 1002 and the RFID toll module 1005 is bywireless near field communication (NFC), such as that specified byISO/IEC 18000-3 which has an effective range of about 10 cm and operatesat 13.56 MHz. Other known NFC protocols can be used equivalently. TheRFID toll module 1005 includes an NFC interface 1006 that cancommunicate, using the NFC protocol, with the mobile device 1002. TheNFC interface is coupled to the processor 1012 that configured a RFIDtag 1014. When the mobile phone 1002 is approaching a toll station, itcommunicates with the RFID toll module 1005 and commands it to configurethe RFID tag 1014 to be read by the toll reader. Upon receiving a tollreader signal, the RFID tag 1014 responds 1016 with an identifier thatunique to the RFID tag 1014 (or that can be assigned or provided by thetoll application). Once the RFID tag 1014 is read, the processor 1012receives the transaction information and forwards it over the NFCinterface 1006 which in turn transmits it via link magnetic link 1008 tothe toll application on the mobile device 1002. The mobile device inturn transmits the transaction information to the toll service backendserver (not shown).

Generally, in operation, when the RFID tag is read, the RFID tagidentifier is sent to the toll service backend server in encrypted formalong with the identifier of the mobile device. The toll service backendserver verifies whether the device is already registered with the tollservice, and if so, whether it belongs to the user of the mobile device,to someone else who is registered to the toll service, or whether it isan unregistered device. If the device is new and unregistered, then theuser is asked to register device by entering all user and mobile devicerelated information. Each account can have several users registered tothe account so that different mobile devices and different RFID tollmodules can be used with the same account. Any unregistered devices willbe denied transaction settlement.

Using the toll application, the user can control billing, make payments,track payment history, update account info, manage organizationalsub-accounts, check usage transaction history, and request customizedexpense reports to be sent to their email either in Excel or as a PDFformat, or as an SMS Message to their phone or mobile device. If thetoll application detects that the user's account contains insufficientfunds for a transaction, the toll application can send a N/ACK ornull-acknowledgment to the RFID toll module's processor to disable theRFID tag, and then toll reader signals will essentially be ignored.However, this can be avoided if an ACK or acknowledgment of the presenceof sufficient funds is communicated to the RFID toll module's processor.

The RFID toll module can be cross-system compatible by including aplurality of RFID tags in the RFID toll module. Each of whichcorresponds to a different toll agency, or a different protocol. Eachdifferent RFID tag can use a different protocol and radio frequency tosupport communication with a specific toll agency operating on thetollway that the mobile device is presently located. Hence the systemcan be compatible over multiple hardware and software systems.

Several different designs may be adopted for the antenna of the RFIDtoll module, depending on the intended range of detection, intendedsignal strength and speed of communication, and the frequency beingused. It is to be noted that the antenna should be placed as far away aspossible from the cellular transceiver antenna in order to avoidinterference.

The toll service can utilize various business rules, such as, forexample, utilizing batch processing of toll transactions. In someembodiments the toll service, by analyzing the user's behavior (e.g.routes travelled, times travelled, etc.) to generate and offer specialoffers through either the toll service or third party providers,depending on the user's pattern of travel or time travelled. This kindof “context-based content” can be sent to a user's account and mobiledevice in the form of coupons or special offers either through email ortext messaging.

In the foregoing specification, specific embodiments have beendescribed. However, one of ordinary skill in the art appreciates thatvarious modifications and changes can be made without departing from thescope of the invention as set forth in the claims below. Accordingly,the specification and figures are to be regarded in an illustrativerather than a restrictive sense, and all such modifications are intendedto be included within the scope of present teachings.

The benefits, advantages, solutions to problems, and any element(s) thatmay cause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as a critical, required, or essentialfeatures or elements of any or all the claims. The invention is definedsolely by the appended claims including any amendments made during thependency of this application and all equivalents of those claims asissued.

Moreover in this document, relational terms such as first and second,top and bottom, and the like may be used solely to distinguish oneentity or action from another entity or action without necessarilyrequiring or implying any actual such relationship or order between suchentities or actions. The terms “comprises,” “comprising,” “has”,“having,” “includes”, “including,” “contains”, “containing” or any othervariation thereof, are intended to cover a non-exclusive inclusion, suchthat a process, method, article, or apparatus that comprises, has,includes, contains a list of elements does not include only thoseelements but may include other elements not expressly listed or inherentto such process, method, article, or apparatus. An element proceeded by“comprises . . . a”, “has . . . a”, “includes . . . a”, “contains . . .a” does not, without more constraints, preclude the existence ofadditional identical elements in the process, method, article, orapparatus that comprises, has, includes, contains the element. The terms“a” and “an” are defined as one or more unless explicitly statedotherwise herein. The terms “substantially”, “essentially”,“approximately”, “about” or any other version thereof, are defined asbeing close to as understood by one of ordinary skill in the art, and inone non-limiting embodiment the term is defined to be within 10%, inanother embodiment within 5%, in another embodiment within 1% and inanother embodiment within 0.5%. The term “coupled” as used herein isdefined as connected, although not necessarily directly and notnecessarily mechanically. A device or structure that is “configured” ina certain way is configured in at least that way, but may also beconfigured in ways that are not listed.

It will be appreciated that some embodiments may be comprised of one ormore generic or specialized processors (or “processing devices”) such asmicroprocessors, digital signal processors, customized processors andfield programmable gate arrays (FPGAs) and unique stored programinstructions (including both software and firmware) that control the oneor more processors to implement, in conjunction with certainnon-processor circuits, some, most, or all of the functions of themethod and/or apparatus described herein. Alternatively, some or allfunctions could be implemented by a state machine that has no storedprogram instructions, or in one or more application specific integratedcircuits (ASICs), in which each function or some combinations of certainof the functions are implemented as custom logic. Of course, acombination of the two approaches could be used.

Moreover, an embodiment can be implemented as a computer-readablestorage medium having computer readable code stored thereon forprogramming a computer (e.g., comprising a processor) to perform amethod as described and claimed herein. Examples of suchcomputer-readable storage mediums include, but are not limited to, ahard disk, a CD-ROM, an optical storage device, a magnetic storagedevice, a ROM (Read Only Memory), a PROM (Programmable Read OnlyMemory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM(Electrically Erasable Programmable Read Only Memory) and a Flashmemory. Further, it is expected that one of ordinary skill,notwithstanding possibly significant effort and many design choicesmotivated by, for example, available time, current technology, andeconomic considerations, when guided by the concepts and principlesdisclosed herein will be readily capable of generating such softwareinstructions and programs and ICs with minimal experimentation.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in various embodiments for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed embodiment. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separately claimed subject matter.

We claim:
 1. A system for automated payment of tolls, comprising: a toll reader at a toll station; a RFID toll module that is communicatively coupled to a mobile device, the mobile device executing a toll application, the RFID toll module including at least one RFID tag that is configured to communicate with the toll reader using a RFID protocol for a toll transaction, wherein the at least one RFID tag communicates an identifier to the toll reader in response to being read by the toll reader during the toll transaction, wherein the RFID toll module communicates transaction information to the toll application on the mobile device upon completion of the toll transaction; and a toll service backend server that maintains a toll account associated with the mobile device, and to which the toll application on the mobile device communicates the transaction information; and wherein the toll service backend reconciles payment of the toll with a toll agency that operates the toll reader, using funds from the toll account.
 2. The system of claim 1, wherein the RFID toll module is associated with the toll account at the toll service backend server, wherein the association is a one-one relationship and the RFID toll module will not function with a mobile device that is not also associated with the toll account.
 3. The system of claim 1, wherein the RFID toll module is designed as a sleeve that fits over the mobile device, and wherein the RFID toll module and the mobile device are connected by at least one of an audio jack, a micro universal serial bus (USB) connection, a micro-high definition media interface (HDMI) connection, a proprietary phone connector, a short range wireless radio connection, an integrated dongle, or acoustic communication channel.
 4. The system of claim 1, wherein the RFID toll module is embedded in the mobile device.
 5. The system of claim 1, wherein the mobile device further include a satellite location receiver for determining a location of the mobile device, the system further comprises predictive functionality which utilizes the location of the mobile device to determine that the mobile device is approaching the toll station, wherein the mobile device enables the RFID toll module in anticipation of being read by the toll reader.
 6. The system of claim 5, wherein one of the at least one RFID tag is selected based on the location of the mobile device.
 7. The system of claim 1, wherein the toll service backend server uses location information reported by the mobile device for the transaction to verify a location of the toll station.
 8. The system of claim 1, wherein the backend server includes a web server that allows a user to access the toll account and to add funds to the toll account.
 9. The system of claim 1, wherein the RFID protocol is selected from a plurality of RFID protocols stored on the RFID toll module.
 10. The system of claim 7, wherein the toll service backend maintains a record of locations of the mobile device.
 11. A toll service backend server, comprising: at least one processor that executes instruction code that causes the toll service backend server to: maintain a toll account that is associated with a mobile device and that includes funds used to pay tolls on behalf of a user of the mobile device; receive toll transaction information from the mobile device; and reconcile toll payment with a toll agency by communicating with a toll agency backend server, wherein toll payment is performed by debiting the toll account for each toll transaction and forwarding funds from the toll account to the toll agency backend server.
 12. The toll service backend server of claim 11, wherein the toll service backend server further receives from the mobile device periodic location updates that indicate a location of the mobile device, and based on the location of the mobile device the toll service backend server determines that the mobile device is approaching a toll station.
 13. The toll service backend server of claim 11, wherein the toll service backend server maintains a record of locations of the mobile device. 